2015-05-04 - 18928.100 - Enhancement - New BPC Rollup Customer Characteristic #FinanceControlling
SPECIFICATIONS
18928.100 - New BPC Rollup Customer Characteristic
Purpose
Need to add new BPC Rollup Customer Characteristic in ZBPC_PLAN infocube.
Admin Info
Purpose
|
Need to add new BPC Rollup Customer Characteristic in ZBPC_PLAN.
|
Requested By
|
Mark Harris
|
Spec Created By
|
Naveen Gadde
|
Spec Created Date
|
05/04/2015
|
Spec QA by
|
Uday Kumar P
|
Objects
|
0CUSTOMER and ZBPC_PLAN
|
Document Status
|
Complete
|
Estimates
SNo
|
Activity
|
Estimation in Hours
|
1
|
Research
|
01
|
2
|
Documentation
|
02
|
3
|
Development/ Config
|
08
|
4
|
Unit test in DEV
|
02
|
5
|
Unit test in QUA
|
01
|
6
|
Other activity
|
02
|
|
TOTAL
|
16
|
References
Prior Tickets
None
Documents
None
Spec Changes
SNo
|
Change Details
|
Requested By
|
Requested On
|
Notes if any
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Requirement
Purpose/WHY:
Email from Greg on 05/05/2015:
Please make the below request HIGH priority. Please review when you come in, and start development and ask any questions you may have.
The below screen shot shows a group of 9* customers. We need to be able to roll these customers into a new characteristic. We don’t want to do this in the current characteristic because the current view of data is still needed occasionally. So we need to create a new characteristic called BPC Customers Lvl 2 [ZBPCCUS2] that will encompass an “ultimate” “all-others” grouping.
ZBPCCUS2 should be added to 0customer and populated in a similar matter that ZBPCCUS is populated, but anything not identified as existing in ZSAPID should go to a customer ID 9199999.
Something like thiswould do the trick and align the data for actuals:
LOOP AT RESULT_PACKAGE INTO WA_RESULT_FIELDS.
SELECT SINGLE /BIC/ZCONSID FROM /BIC/PZSAPID INTO WA_RESULT_FIELDS-/BIC/ZBPCCUS2
WHERE /BIC/ZSAPID = WA_RESULT_FIELDS-CUSTOMER
AND /BIC/ZINDID = 'CUS'.
IF SY-SUBRC NE 0.
WA_RESULT_FIELDS-/BIC/ZBPCCUS2 = '9199999'.
ENDIF.
ENDLOOP.
On the other hand for budget data, we’ll have to put ZBPCCUS2 in ZBPC_PLAN and create some code to make all CU_9* customers roll up to 9199999:
In Scope:
Need to add ZBPCCUS2 in 0CUSTOMER Master data infoobject & ZBPC_PLAN Infocube.
Out of Scope:
None
Solution Summary
1. Need to add Customer level 2 infoobject in Customer master data & BPC Budget data infocube.
2. Need to write necessary logic to populate all Customers starting with 9 into "9199999".
3. Need to add the Customer level 2 infoobject in both the Global & Regional BPC Multiproviders.
4. Need to collect all the changes into transport requests.
5. Need to reload the data for BPC Budget data Infocube once all the transports are moved to production.
Test Plan
SNo
|
Test Scenario
|
Expected Results
|
1
|
Check if ZBPCCUS2 is added in 0CUSTOMER & ZBPC_PLAN.
|
ZBPCCUS2 should be added to 0CUSTOMER & ZBPC_PLAN.
|
2
|
Check if data is populated for ZBPCCUS2 as per the logic defined.
|
ZBPCCUS2 should be populated as per the logic defined.
|
3
|
Check if all the objects are collected into the transport request.
|
All the objetcs shold be collected into the transport request.
|
Solution Details
1. Need to add ZBPCCUS2 infoobject in 0CUSTOMER master data & ZBPC_PLAN infocube.
2. Need to write necessary logic to populate all Customers starting with 9 into "9199999".
3. Need to add the ZBPCCUS2 infoobject in both the Global & Regioanl BPC Multiproviders.
4. Need to collect all the changes into transport requests.
5. Need to reload the data for ZBPC_PLAN Infocube once all the transports are moved to production.
Issues
None